This chapter describes how to use the software. It consists of:
When typing a command, remember the following:
When you start the device, the console displays a boot message. The OPCON prompt (*) then appears on the screen indicating that you are in the OPCON process and you can begin entering OPCON commands. This is the command prompt from which you communicate with different processes.
Commands that are needed more often appear before the "- - - - -" separator. Enter the appropriate command at the OPCON prompt (*). See Table 4 for a list of commands.
Alternatively, you can:
The status command displays information about the device processes, such as the process IDs (PIDs), process names and status of the process. Issuing the status command is shown in the following example:
* status
Pid Name Status TTY Comments
1 COpCn1 RDY TTY0
2 Monitr DET --
3 Tasker RDY --
4 MOSDBG DET --
5 CGWCon DET --
6 Config DET --
7 ELScon DET --
8 ROpCn1 IDL TTY1 128.185.210.125
9 ROpCn2 IDL TTY2
| Note: | Not every process listed has a user interface (for example, the talk 3 process). The talk 4 command is for use by IBM service representatives. |
Each process uses a different prompt. You can tell which process your console is connected to by looking at the prompt. (If the prompt does not appear when you enter the talk pid command, press Enter again.)
The following list shows the prompts for the five main processes:
Table 2. Processes, Their Purpose, and Commands to Access
| Process | Level and Purpose | Command to Access | Input Prompt | ||
|---|---|---|---|---|---|
| OPCON | Level 1 - access to all secondary levels | Ctrl-P | asterisk (*) | ||
| CONFIG | Level 2 - base services configuration and access to configuration third level | Configuration or talk 6 | Config > | ||
| GWCON | Level 2 - base services operation and monitoring and access to operations and monitoring on third level | Console or talk 5 | plus sign (+) | ||
| MONITR | Level 2 - message display | Event or talk 2 | (none) | ||
| ELSCon | Level 2 - direct monitoring and access to ELS console | els or talk 7 | ELS Secondary Console> | ||
| MOSDBG | Level 2 - diagnostic environment | talk 4 | db> | ||
| DIAGS | Level 2 - run hardware diagnostics | diags |
| ||
| |||||
At the OPCON prompt level, you can begin to enter commands from the keyboard. Use the Backspace key to delete the last character typed in on the command line. Use Ctrl-U to delete the whole command line entry so that you can reenter a command. See "Command Completion" and "Command History" for additional details or press Escape ?.
At the command prompts, you can obtain help in the form of a listing of the commands available at that level. To do this, type ? (the help command), and then press Enter. Use ? to list the commands that are available from the current level. You can usually enter a ? after a specific command name to list its options.
The multiple-level nature of the software places you in secondary, tertiary, and even lower level environments as you configure or operate the 2216. To return to the next higher level, enter the exit command. To get to the secondary level, continue entering exit until you receive the secondary level prompt (either Config> or +).
For example, to exit the ASRT protocol configuration process:
ASRT config> exit Config>
If you need to get to the primary level (OPCON), enter the intercept character (Ctrl-P by default).
To get back to the OPCON prompt (*), press Ctrl-P. You must always return to OPCON before you can communicate with another process. For example, if you are connected to the console (GWCON) process and you want to connect to the CONFIG process, you must press Ctrl-P to return to OPCON first. The Ctrl-P key combination is the default intercept character.
If you use the intercept character from a third-level or lower level menu to return to the * prompt, the next time you use the talk command to talk to the same process, you will reenter that same level menu. This link goes away when the device is re-initialized.
Configuring a 2216 is different depending on whether you are configuring for the first time, creating a configuration based on an existing configuration, or just updating a configuration. Use the following sections as a guide to the best procedure to use, depending on your needs.
This procedure assumes that you have no other 2216 that contains a configuration similar to the one for the 2216 you are configuring. The procedure also assumes that you have just taken the 2216 out of the box. Although this procedure specifies an order, you can perform the actual configuration (after step 3) in any order.
To configure a IBM 2216 for the first time:
| Note: | At the very least, you will configure IP in this step. |
This section describes how to:
If you already have a 2216 that has the same interfaces, features, and protocols that you want to configure on a new 2216, you can save time by basing the configuration on the existing 2216. You can perform this type of configuration either using the command line interface or by using the configuration program that comes with the 2216. In both cases, the procedures assume that the 2216 is not in your production network.
To base a configuration on an existing configuration using the command line interface:
To base a configuration on an existing configuration using the configuration program:
For more about using the configuration program, see Configuration Program User's Guide for Nways Multiprotocol and Access Services Products GC30-3830.
To permanently update a configuration:
The ability to temporarily update a configuration allows you to make changes to some of the operating characteristics of a 2216 until you can make permanent updates to the configuration. This enables you to implement changes immediately to resolve problems or improve performance and avoid an outage during a peak period. You can then make permanent updates to the configuration and schedule an outage so you can reload to pick up the change.
To temporarily update a configuration:
| Note: | Not all interface types, protocols, or features allow you to make temporary config changes via talk 5 commands. |
All interfaces, features, and protocols have commands that you use to access the following processes:
You can also configure or operate some base system services through the second-level processes. The commands to perform these functions are described starting in What is CONFIG?.
The next sections describe the procedures for accessing the second-level processes.
Each protocol configuration process is accessed through the device's CONFIG process. CONFIG is the second-level process of the device user interface that lets you communicate with third-level processes. Protocol processes are examples of third-level processes.
The CONFIG command interface is made up of levels of menus. Protocol configuration command interfaces are menus within the CONFIG interface. Each protocol configuration interface has its own prompt. For example, the prompt for the SNMP protocol command interface is SNMP config>.
The next sections describe these procedures in more detail.
To enter the CONFIG process from OPCON and obtain the CONFIG prompt, enter the configuration command. Alternatively, you can enter the OPCON talk command and the PID for CONFIG. The PID for CONFIG is 6.
* configuration
or
* talk 6
The console displays the CONFIG prompt (Config>). If the prompt does not appear, press the Enter key again.
Quick Configuration, or Quick Config, allows you to quickly configure portions of the device without dealing with the specific operating system commands. You enter the Quick Config menus from the CONFIG process using the qconfig command (see Quick Configuration).
Changes that you make to the protocol parameters through CONFIG do not take effect until you either activate the net that contains any dynamic changes or reload the device software.
| Note: | You must enter the write command to save the changes in the device's flash memory. |
To view information about the interfaces, features, or protocols or to change parameters while running, you must access and use the operating (monitoring) process. Operating command interfaces are modes of the GWCON interface. Within the GWCON mode, each interface, feature, or protocol interface has its own prompt. For example, the prompt for the SNMP protocol is SNMP>.
| Note: | Any parameters you change in this process will not remain active across any event that causes the 2216 to reload the operational code, such as a power outage or entering the reload command. |
The next sections describe these procedures in more detail.
To enter the GWCON process from OPCON and obtain the GWCON prompt, enter the console command. Alternatively, you may enter the talk command and the PID for GWCON. The PID for GWCON is 5. For example:
* console
or
* talk 5
The GWCON prompt (+) then displays on the console. If the prompt does not appear, press Enter again.
The Secondary ELS Console provides convenient access to GWCON talk 5 ELS without disrupting the current state of GWCON. You may be in the middle of a ping in talk 5, or deep inside a talk 5 menu structure, and want to control ELS without disrupting the current state of GWCON. The secondary ELS console (Talk 7) serves this purpose.
To enter the Secondary ELS Console (ELScon) process from OPCON and obtain the Secondary ELS Console prompt, enter the els command. Alternatively, you may enter the talk 7 command.
In the following example, another ELS event is displayed while performing a ping command.
| Note: | The intercept character (Ctrl-P by default) is used to obtain the OPCON prompt (*). |
*talk 5
+protocol ip
IP>ping 10.0.0.9
PING 10.0.0.2 -> 10.0.0.9: 56 data bytes, ttl=64, every 1 sec.
*talk 7
ELS Secondary Console>display event ip.7
Complete
ELS Secondary Console>
*talk 2
00:20:48 IP.007: 10.0.0.2 -> 10.0.0.9
00:20:49 IP.007: 10.0.0.2 -> 10.0.0.9
After accessing the second level, you must enter commands on the third level to configure or operate the interfaces, features, and protocols in your IBM 2216. The following sections describe how to access the third level processes.
This section describes how to use the add device command to configure the network interfaces. A network interface is usually an adapter, but it can also be a definition used by an operating process. For example, two IP addresses can be assigned to one port and each one is considered an interface. After you establish an interface using the add device command, you can access the network interface configuration and operating processes, for example, the Talk 5 monitoring processes. These processes are used to change and monitor the software-configurable parameters for the network interfaces that are used in your device.
Use the following procedure to access the device's configuration process. This process gives you access to a specific interface's configuration process.
* configuration
After you enter the configuration command, the CONFIG prompt (Config>) displays on the console. If the prompt does not appear when you first enter configuration, press Enter again.
Use the add device command to create a network interface. The add device command automatically assigns the interface number. (Enter add device ? to get a list of the supported device types.)
These are the types of devices that are supported:
When you specify a multi-port adapter device name with the add device command, you are prompted for the adapter's slot number and the port number on the adapter that you want to use for the interface.
If you want to use multiple ports on an adapter, you must enter the add device command multiple times and specify a different port number each time.
For example, you would enter the following commands to create interfaces for ports 0 and 1 on the 8-port X.21 adapter in slot 7.
Config> add device x21 Device Slot #(1-8) [1]? 7 Device Port #(0-7) [0]? 0 Defaulting Data-link protocol to PPP Adding X.21 PPP device in slot 7 port 0 as interface #6 Use "set data-link" command to change the data-link protocol Use "net 6" to configure X.21 PPP parameters Config> add device x21 Device Slot #(1-8) [1]? 7 Device Port #(0-7) [0]? 1 Defaulting Data-Link protocol to PPP Adding X.21 PPP device in slot 7 port 1 as interface #7 Use "set data-link" command to change the data-link protocol Use "net 7" to configure X.21 PPP parameters
| Note: | The serial adapter port numbers are 0-based. The port numbers for all other multi-port adapters are 1-based. |
The 4-port ISDN Channelized T1 and E1 adapters allow you to configure multiple ports with one add device command. When you add one of these adapters, the software will prompt you for a range of ports to add. The following example shows how you would add a 4-port ISDN Channelized T1 and E1 adapter into slot 4 that is using dial-in nets:
Device Slot #(1-8) [1]? 3 Device Port Range (1-8) Lowest Port #(1) [1]? 2 Highest Port #(8) [8]? 2 Automatically add dial-in nets for this base net? (Yes or [No]): yes Automatically enable IP for these dial-in nets?(Yes or [No]): yes Enable as a Multilink PPP link?(Yes or [No]): yes Adding 23 dial-in nets on top of base net 14 Adding 8-port ISDN Primary T1/J1 devices in slot 3 port 2 as interfaces #14. Use "net 14" to configure 8-port ISDN Primary T1/J1 parameters.
When you specify a single-port adapter device name with the add device command, you are prompted for the adapter's slot number.
The following example adds an interface for the 1-port ISDN-PRI T1/J1 adapter in slot 2:
Config> add device t1-isdn Device Slot #(1-8) [1]? 2 Adding ISDN Primary T1/J1 device in slot 2 port 1 as interface #7 Use "net 7" to configure ISDN Primary T1/J1 parameters
The following example adds a dial circuit interface:
Config> add device dial-circuit Enter the number of PPP Dial Circuit interfaces [1]? Adding device as interface 8 Base net for this circuit[0]?4 Defaulting Data-link protocol to PPP Use "set data-link" command to change the data-link protocol Use "net 8" command to configure circuit parameters
Config>add device dial-in Enter the number of dial-in interfaces [1]? Adding device as interface 5 Base net for this circuit [0]? 5 Defaulting Data-link protocol to PPP Use "set data-link" command to change the data-link protocol Use "net 5" command to configure circuit parameters
The following example adds a multilink PPP interface:
Config>add device multilink-ppp Enter the number of Multilink PPP interfaces [1]? Adding device as interface 7 Defaulting Data-link protocol to PPP Use "net 7" command to configure circuit parameters
Notes:
Config> list devices Ifc 0 Token Ring Slot: 1 Port: 1 Ifc 1 Token Ring Slot: 1 Port: 2 Ifc 2 Token Ring Slot: 2 Port: 1 Ifc 3 Token Ring Slot: 2 Port: 2 Ifc 4 Ethernet Slot: 4 Port: 1 Ifc 5 Ethernet Slot: 4 Port: 2 Ifc 6 Ethernet Slot: 5 Port: 1 Ifc 7 Ethernet Slot: 5 Port: 2 Ifc 8 Ethernet Slot: 6 Port: 1 Ifc 9 Ethernet Slot: 6 Port: 2 Ifc 10 V.35/V.36 Frame Relay Slot: 8 Port: 0 Ifc 11 V.35/V.36 X.25 Slot: 8 Port: 1 Ifc 12 V.35/V.36 PPP Slot: 8 Port: 2 Ifc 13 V.35/V.36 PPP Slot: 8 Port: 3 Ifc 14 V.35/V.36 PPP Slot: 8 Port: 4 Ifc 15 V.35/V.36 PPP Slot: 8 Port: 5
Config> network 1
The appropriate configuration prompt (such as TKR Config> for token-ring), now displays on the console.
| Note: | Not all network interfaces are user-configurable. For interfaces that
cannot be configured, you receive the message:
That network is not configurable |
IBM 2216 Device Support Restrictions: The following rules apply when adding devices to the IBM 2216:
Displaying the Interface Configuration:
From the same interface configuration prompts, you can list configuration information specific to that selected interface by using the list command. For example:
TKR Config> list
Token-Ring configuration:
PACKET SIZE (INFO FIELD): 4472
Speed: 16 Mb/sec
Media: Shielded
RIF Aging Timer: 120 Source Routing: Enabled
MAC Address: 000000000000
Configuring the Network Interface:
Refer to the specific chapters in this guide for complete information on configuring your IBM 2216's network interfaces.
Table 3 lists network architectures and the supported interfaces for
each architecture.
Table 3. Network Architecture and the Supported Interfaces
| Network Architecture | Supported Interfaces | ||
|---|---|---|---|
| ATM | 1-Port ATM 155-Mbps MMF
1-Port ATM 155-Mbps SMF | ||
| 802.5 Token-Ring | 2-Port Token-Ring | ||
| Ethernet |
| ||
| ISDN |
Notes:
| ||
| Point-to-Point | 8-port V.24/EIA 232E, 6-port V.35/V.36, 8-port X.21, 1-port HSSI, and dial circuit interfaces | ||
| Frame Relay | 8-port V.24/EIA 232E, 6-port V.35/V.36, 8-port X.21, 1-port HSSI, and dial circuit interfaces | ||
| X.25 | 8-port V.24/EIA 232E, 6-port V.35/V.36, and 8-port X.21 adapters | ||
| SDLC Relay | 8-port V.24/EIA 232E, 6-port V.35/V.36, and 8-port X.21 | ||
| SDLC | 8-port V.24/EIA 232E, 6-port V.35/V.36, 8-port X.21, and dial circuit interfaces | ||
| V.25bis | 8-port V.24/EIA 232E | ||
| Dial-In | A PPP dial circuit interface that has configuration parameters defaulted to support DIALs | ||
| Multilink PPP (MP) | Supported on any PPP link | ||
| ESCON Channel Adapter | LAN Channel Station (LCS), Link Services Architecture (LSA), and Multi-Path Channel+ (MPC+) | ||
| Parallel Channel Adapter | LAN Channel Station (LCS), Link Services Architecture (LSA), and Multi-Path Channel+ (MPC+) | ||
| L2TP, L2F, and PPTP | Supports virtual PPP DIALs connections through the Layer 2 Tunneling Protocol (L2TP), Layer 2 Forwarding (L2F), and Point to Point Tunneling Protocol (PPTP). | ||
| FDDI | 1-port FDDI |
Notes:
To monitor information related to a specific device, access the console process by using the following procedure:
* console
+configuration Multiprotocol Access Services 2216-MAS Feature 2822 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF9 cc4_2a Num Name Protocol 0 IP DOD-IP 3 ARP Address Resolution 4 DN DNA Phase IV 6 VIN Banyan Vines 7 IPX NetWare IPX 10 BGP Border Gateway Protocol 11 SNMP Simple Network Management Protocol 12 OSPF Open SPF-Based Routing Protocol 22 AP2 AppleTalk Phase 2 23 ASRT Adaptive Source Routing Transparent Enhanced Bridge 26 DLS Data Link Switching 27 XTP X.25 Transport Protocol 28 APPN Advanced Peer-to-Peer Networking [HPR] 30 APPN Advanced Peer-to-Peer Networking [ISR] Num Name Feature 2 MCF MAC Filtering 16 Networks: Net Interface MAC/Data-Link Hardware State 0 TKR/0 Token-Ring/802.5 Token-Ring Up 1 TKR/1 Token-Ring/802.5 Token-Ring Up 2 TKR/2 Token-Ring/802.5 Token-Ring Up 3 TKR/3 Token-Ring/802.5 Token-Ring Up 4 Eth/0 Ethernet/IEEE 802.3 Ethernet Up 5 Eth/1 Ethernet/IEEE 802.3 Ethernet Up 6 Eth/2 Ethernet/IEEE 802.3 Ethernet Up 7 Eth/3 Ethernet/IEEE 802.3 Ethernet Up 8 Eth/4 Ethernet/IEEE 802.3 Ethernet Up 9 Eth/5 Ethernet/IEEE 802.3 Ethernet Up 10 FR/0 Frame Relay V.35/V.36 Up 11 X25/0 X.25 V.35/V.36 Up 12 PPP/0 Point to Point V.35/V.36 Up 13 PPP/1 Point to Point V.35/V.36 Up 14 PPP/2 Point to Point V.35/V.36 Up 15 PPP/3 Point to Point V.35/V.36 Up
+ network 11 X.25>
In this example, the X.25 console prompt is displayed on the console. You can then view information about the X.25 interface by entering the X.25 console commands.
Monitoring the Network Interface:
Refer to the specific chapters in this manual for complete information on monitoring your 2216's network interfaces.
To help you access the Multiprotocol Access Services feature configuration and operating processes, this section outlines both of these procedures.
Use the feature command from the CONFIG process to access configuration commands for specific Multiprotocol Access Services features outside of the protocol and network interface configuration processes.
Use the feature command from the GWCON process to access console commands for specific features that are outside of the protocol and network interface console processes.
Enter a question mark after the feature command to display a listing of the features available for your software release. For example:
Config> feature ?
WRS
BRS
MCF
TSF
Feature name or number [1] ?
To access a particular feature's configuration or operating prompt, enter the feature command at the Config> or + (GWCON) prompt, respectively, followed by the feature number or short name. For example:
Config> feature mcf
MAC filtering user configuration
Filter Config>
Table 9 lists the available feature numbers and names.
Once you access the configuration or operating prompt for a feature, you can begin entering specific commands for the feature. To return to the previous prompt level, enter the exit command at the feature's prompt.
This section describes how to access the protocol configuration and operating processes.
To enter the desired protocol configuration process from the CONFIG> prompt:
Config> protocol SNMP
or
Config> protocol 11 SNMP user configuration
The protocol configuration prompt then displays on the console. The following example shows the SNMP protocol configuration prompt:
SNMP config>
You can now begin entering the protocol's configuration commands. See the corresponding protocol section of the Protocol Configuration and Monitoring Reference for more information on specific protocol configuration commands.
In summary, the protocol command lets you enter the configuration process for the protocol software installed in your device. The protocol command enters a protocol's command process. After entering the protocol command, the prompt of the specified protocol appears. From the prompt, you can enter commands specific to that protocol.
To enter a protocol console process from the GWCON prompt:
+configuration Multiprotocol Access Services 2216-MAS Feature 2822 V3.2 Mod 0 PTF 0 RPQ 0 MAS.EF9 cc4_2a Num Name Protocol 0 IP DOD-IP 3 ARP Address Resolution 4 DN DNA Phase IV 6 VIN Banyan Vines 7 IPX NetWare IPX 10 BGP Border Gateway Protocol 11 SNMP Simple Network Management Protocol 12 OSPF Open SPF-Based Routing Protocol 22 AP2 AppleTalk Phase 2 23 ASRT Adaptive Source Routing Transparent Enhanced Bridge 26 DLS Data Link Switching 27 XTP X.25 Transport Protocol 28 APPN Advanced Peer-to-Peer Networking [HPR] 30 APPN Advanced Peer-to-Peer Networking [ISR] Num Name Feature 2 MCF MAC Filtering 16 Networks: Net Interface MAC/Data-Link Hardware State 0 TKR/0 Token-Ring/802.5 Token-Ring Up 1 TKR/1 Token-Ring/802.5 Token-Ring Up 2 TKR/2 Token-Ring/802.5 Token-Ring Up 3 TKR/3 Token-Ring/802.5 Token-Ring Up 4 Eth/0 Ethernet/IEEE 802.3 Ethernet Up 5 Eth/1 Ethernet/IEEE 802.3 Ethernet Up 6 Eth/2 Ethernet/IEEE 802.3 Ethernet Up 7 Eth/3 Ethernet/IEEE 802.3 Ethernet Up 8 Eth/4 Ethernet/IEEE 802.3 Ethernet Up 9 Eth/5 Ethernet/IEEE 802.3 Ethernet Up 10 FR/0 Frame Relay V.35/V.36 Up 11 X25/0 X.25 V.35/V.36 Up 12 PPP/0 Point to Point V.35/V.36 Up 13 PPP/1 Point to Point V.35/V.36 Up 14 PPP/2 Point to Point V.35/V.36 Up 15 PPP/3 Point to Point V.35/V.36 Up
| Note: | APPN(R) is a registered trademark of IBM. |
In the following example, the command has been entered for accessing the SNMP protocol console process.
+ protocol 11
or
+ protocol SNMP
The protocol console prompt then displays on the console. This example shows the SNMP protocol console prompt:
SNMP>
You can now begin entering the protocol's commands. See the corresponding protocol section of the Protocol Configuration and Monitoring Reference for more information on specific protocol console commands.
The automatic command completion function assists you with the syntax for commands entered at the command line.
To illustrate the behavior of Command Completion, assume that the following commands are allowed in a given menu context. (This is an example menu only.)
caching
cache-timeout
priority
The following online help is available when command-completion is enabled.
See page *** for the enable command-completion syntax.
The following rules apply to automatic command completion:
The following online help is available when command-completion is disabled:
Command Completion is currently Disabled. To Enable this option, use the enable command-completion command from Configuration talk 6.
The Command History contains up to the last 50 commands entered by the user in OPCON, GWCON (Talk 5) or CONFIG (Talk 6) command line menus.
Backward and Forward retrieve keys can be used to recall previously entered commands. In addition, a facility is provided to enable the advanced user to repeat a particular series of commands.
By pressing Ctrl-B (backward) or Ctrl-F (forward) at any command line prompt in an OPCON, GWCON or CONFIG menu, the current command line is replaced by the previous or next command in the Command History. The Command History is common across the command line interface. That is, a command entered while in a GWCON menu can be retrieved from within CONFIG and a command entered while in a CONFIG menu can be retrieved from within GWCON.
When automatic Command Completion is enabled (See"Command Completion") and a Command History retrieve key (Ctrl-B,F,N) is pressed, the Command History is scanned for a command that successfully parses in the current command context. A tone will be sounded if no such command exists.
The Command History contains the most recently entered commands, up to a maximum of the last 50 commands. If only three commands have been entered since a restart, pressing Ctrl-F or Ctrl-B circles through only those three commands. If no commands have been entered thus far, Ctrl-F or Ctrl-B results in tone sound.
| Note: | A command aborted by pressing Ctrl-U will not be entered into the Command History. When Command Completion is enabled, only complete commands are entered into the Command History. |
To enter two similar commands:
display sub les
display sub lec
Enter:
display sub les, then press Enter
Ctrl-B for Backward, and the current line is replaced with-
display sub les
Press Backspace and replace "s" with "c" to get
display sub lec and then press Enter
There is an additional feature for advanced users to facilitate repeating a particular series of GWCON or CONFIG commands. C1, C2,...,Cn in the Command History is referred to as a repeat sequence. This feature may be more convenient than simply using Ctrl-B and Ctrl-F when you must repeat a given task that requires multiple commands. Enter Ctrl-R (repeat) to set the start of the repeat sequence at command C1. Enter Ctrl-N (next) successively to retrieve the next command in the repeat sequence. Commands are not automatically entered, but are placed on the current command line allowing you to modify or enter the command.
To produce the desired behavior of a repeat sequence, the first command retrieved using the first Ctrl-N (next) depends on the manner in which the start of the repeat sequence was set using Ctrl-R (repeat).
Setting the start of the repeat sequence with Ctrl-R can be done in two ways:
If you enter Ctrl-R as command C1 is being keyed in, and then enter commands C2, C3... Cn. Ctrl-N will successively bring commands C1, C2, ... Cn, C1, C2, ... Cn, C1, ... to the command line.
In Example 1, the start of the repeat sequence is set as the first command is keyed in. The user knows ahead of time that the same commands to be entered in GWCON need to be repeated in CONFIG.
Example 1
*console +event Ctrl-R
then press Enter to set the start of the repeat sequence.
Event Logging System user console ELS>display sub les ELS>display sub lec ELS>exit +
Ctrl-P (the default OPCON intercept character) and go to CONFIG.
+-press Ctrl-P- *configuration Config>Ctrl-N for NEXT to retrieve the start of this sequence- Config>event Enter Event Logging System user configuration ELS config>Ctrl-N for NEXT to retrieve the next command in sequence- ELS config>display sub les Enter ELS config>Ctrl-N for NEXT to retrieve the next command in sequence- ELS config>display sub lec Enter ELS config>Ctrl-N for NEXT to retrieve the next command in sequence- ELS config>exit Enter Config>
On the other hand, if you first enter C1, C2, ... Cn, and retrieve C1 via Ctrl-B or Ctrl-F. Entering Ctrl-R, entering Ctrl-N successively brings commands C2,..., Cn, C1, C2,..., Cn, C1,...,Cn to the command line (see Example 2). The first occurrence of C1 is bypassed since C1 is already available on the command line at the time it was retrieved, and does not need to be recalled again by the first Ctrl-N.
In Example 2, all the commands are entered and then the first command in the sequence to be repeated is retrieved. A sequence of commands has been entered in GWCON, and the same sequence needs to be repeated in CONFIG.
Example 2
*console +event Event Logging System user console ELS>display sub les ELS>display sub lec ELS>exit +
+Ctrl-P-
*configuration
Config>Ctrl-B four times to retrieve the start of
the four command sequence in this example-
Config>event
Config>event Ctrl-R for REPEAT to set the start of the repeat sequence-
Config>event Enter
Event Logging System user configuration
ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
ELS config>display sub les Enter
ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
ELS config>display sub lec Enter
ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
ELS config>exit Enter
Config>